Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

0875

reference: 831-tree-1
name: 0875
tree-preservation-order: undefined
831-tpo-1
uprn
address-text
point: POINT (-1.041871 50.872405)
geometry: MULTIPOLYGON (((-1.041829 50.872400,-1.041831 50.872409,-1.041837 50.872416,-1.041846 50.872422,-1.041858 50.872426,-1.041871 50.872428,-1.041896 50.872423,-1.041906 50.872417,-1.041912 50.872409,-1.041914 50.872401,-1.041912 50.872393,-1.041906 50.872385,-1.041897 50.872379,-1.041885 50.872375,-1.041872 50.872374,-1.041859 50.872375,-1.041847 50.872379,-1.041837 50.872385,-1.041831 50.872392,-1.041829 50.872400)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL